Bluetooth low energy collision management

ABSTRACT

Methods and systems are disclosed for managing the emission of data from RF enabled tags. In an example embodiment, data is emitted from a tag via RF communications. An operation can be implemented to detect one or more non-official applications running on a mobile device (e.g., a nearby mobile device). The emission power level for emitting such data can then be automatically varied until an answer is received from an official application running on another mobile device so as to prevent said mobile device running said non-official application from preventing said official application running on said another mobile device from completing a transaction with respect to said data emitted from said tag via said RF communications.

TECHNICAL FIELD

Embodiments are generally related to BLE (Bluetooth Low Energy) devices,methods, and systems. Embodiments also relate to mobile devices, such assmartphones, tablet-computing devices, and wearable computing devicesand so on, which utilize BLE forms of communication. Embodiments furtherrelate to tags installed on vehicles or gates that allow fortransactions with mobile devices.

BACKGROUND

Ticketing is an essential function in public transportation networks. Aticketing function must successfully address several key requirementsfrom both the travelers and the operator's perspectives. Typicaltraveler requirements may include ease of use (easy to learn and routinein practice), clear and visible pricing, secure with respect to loss,theft or forgery, e.g., ticket books, passes, etc., and privacypreserving. Typical operator requirements of a ticketing function mayinclude user acceptance (barriers to usage can quickly lead to arejection of the transportation system by the public), security(confidentiality of the transaction, authentication and non-repudiation,fraud resistance (amateur and organized)), and high availability.Additional requirements of the operator to ticketing functions willcorrespond to deployment costs, both for infrastructure (readers,validation systems, personnel, etc.) and mobility (tickets, cards, etc.,in the hands of the traveler).

Tags may be employed in such ticketing applications. An example of a tagis disclosed in U.S. Patent Application Publication No. 2014/0201066 toPascal Roux et al., which published on Jul. 17, 2014 and is incorporatedherein by reference in its entirety. In particular, BLE tags may beutilized for transactions such as ticketing or other activities. Any BLEmobile device (e.g., a smartphone) may answer to a BLE tag, which mayprevent the desired mobile device in front of such a tag from making aBLE transaction (e.g., a ticketing or other transaction or activity).The tag power may be reduced to limit this risk. However, a minimumlevel must be kept to guarantee proper operation with any smartphone(and housing) having any sensitivity. The problem may still occur withunwanted smartphones in some proximity of the tag.

BRIEF SUMMARY

The following summary is provided to facilitate an understanding of,some of the innovative features unique to the disclosed embodiments andis not intended to be a full description. A full appreciation of thevarious aspects of the embodiments disclosed herein can be gained bytaking the entire specification, claims, drawings, and abstract as awhole.

It is, therefore, one aspect of the disclosed embodiments to provideimproved RF (Radio Frequency) enabled tags that are capable of beinginstalled on or in for example, vehicles or gates, and which allow fortransactions with mobile devices.

It is another aspect of the disclosed embodiments to provide fordevices, methods, and systems for managing the emission of data fromsuch RF enabled tags for receipt by nearby mobile devices.

It is another aspect of the disclosed embodiments to provide fordevices, methods, and systems for successively using varying powerlevels in order to automatically and quickly find a power level whichallows a communication only with the closest mobile device (i.e., theone willing to make a transaction with respect to the tag).

The aforementioned aspects and other objectives and advantages can nowbe achieved as described herein. A method, apparatus, and system aredisclosed for managing the emission of data (e.g., advertisements,messages, etc.) from RF enabled tags. In an example embodiment, data isemitted from a tag via RF communications. An operation can beimplemented to detect one or more non-official applications running on amobile device (e.g., one or more nearby mobile devices). The emissionpower level for emitting such data can then be automatically varieduntil an answer is received from an official application running onanother mobile device so as to prevent said mobile device running saidnon-official application from preventing said official applicationrunning on said another mobile device from completing a transaction withrespect to said data emitted from said tag via said RF communications.The emission power level can be varied utilizing, for example, adecreasing ramp algorithm or a dichotomy algorithm.

The disclosed approach is based on the fact that a mobile device such asa smartphone may be equipped with a non-official application and theuser of such a smartphone may decide to always answer tag emitted datasuch as advertisements, which can prevent other mobile devices (equippedwith an “official” application) from completing a transaction eventhough such devices may be located directly in front of the tag.

The disclosed embodiments can therefore emit data from a tag withdifferent power levels in order to automatically and quickly find thepower level that allows for a transaction with the closest mobile device(i.e., the mobile device willing to make an “official” transaction). Thetag can be equipped with instructions that instruct the tag to detectnon-official applications that continuously answer and prevent otherofficial applications from answering, and additionally with instructionsthat change the power level (e.g., by using a decreasing ramp or adichotomy algorithm) until it (the tag) receives an answer from anotherofficial application.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying figures, irk which like reference numerals refer toidentical or functionally similar elements throughout the separate viewsand which are incorporated in and form a part of the specification,further illustrate the present invention and, together with the detaileddescription of the invention, serve to explain the principles of thedisclosed embodiments.

FIG. 1 illustrates a block diagram depicting a system for using aplurality of power levels in order to automatically and rapidly find thepower level, which allows a communication only with the closest mobiledevice willing to make a transaction, in accordance with an exampleembodiment;

FIG. 2 illustrates a block diagram depicting a system for using aplurality of power levels in order to automatically and rapidly find thepower level, which allows a communication only with the closest mobiledevice willing to make a transaction, in accordance with an alternativeexample embodiment;

FIG. 3 illustrates a schematic diagram depicting one example embodimentof a mobile device that can be utilized in accordance with an exampleembodiment;

FIG. 4 illustrates a system for improving BLE collision management, inaccordance with an example embodiment;

FIG. 5 illustrates a system for improving BLE collision management, inaccordance with an alternative example embodiment;

FIG. 6 illustrates a flow chart of operations depicting logicaloperational steps of a method for BLE collision management, inaccordance with an example embodiment;

FIG. 7 illustrates a flow chart of operations depicting logicaloperational steps of a decreasing ramp algorithm, in accordance with anexample embodiment; and

FIGS. 8A-8B illustrate a flow chart of operations depicting logicaloperational steps of a dichotomy algorithm, in accordance with anexample embodiment.

DETAILED DESCRIPTION

Subject matter will now be described more fully hereinafter withreference to the accompanying drawings, which form a part hereof, andwhich show, by way of illustration, specific example embodiments.Subject matter may, however, be embodied in a variety of different formsand, therefore, covered or claimed subject matter is intended to beconstrued as not being limited to any example embodiments set forthherein; example embodiments are provided merely to be illustrative.Likewise, a reasonably broad scope for claimed or covered subject matteris intended. Among other things, for example, subject matter may beembodied as methods, devices, components, or systems. Accordingly,embodiments may, for example, take the form of hardware, software,firmware, or any combination thereof (other than software per se). Thefollowing detailed description is, therefore, not intended to beinterpreted in a limiting sense.

Throughout the specification and claims, terms may have nuanced meaningssuggested or implied in context beyond an explicitly stated meaning.Likewise, phrases such as “in one embodiment” or “in an exampleembodiment” and variations thereof as utilized herein do not necessarilyrefer to the same embodiment and the phrase “in another embodiment” or“in another example embodiment” and variations thereof as utilizedherein may or may not necessarily refer to a different embodiment. It isintended, for example, that claimed subject matter include combinationsof example embodiments in whole or in part.

In general, terminology may be understood, at least in part, from usagein context. For example, terms such as “and,” “or,” or “and/or” as usedherein may include a variety of meanings that may depend, at least inpart, upon the context in which such terms are used. Typically, “or” ifused to associate a list, such as A, B, or C, is intended to mean A, B,and C, here used in the inclusive sense, as well as A, B, or C, hereused in the exclusive sense. In addition, the term “one or more” as usedherein, depending at least in part upon context, may be used to describeany feature, structure, or characteristic in a singular sense or may beused to describe combinations of features, structures, orcharacteristics in a plural sense. Similarly, terms such as “a,” “an,”or “the,” again, may be understood to convey a singular usage or toconvey a plural usage, depending at least in part upon context. Inaddition, the term “based on” may be understood as not necessarilyintended to convey an exclusive set of factors and may, instead, allowfor existence of additional factors not necessarily expressly described,again, depending at least in part on context. Additionally, the term“step” can be utilized interchangeably with “instruction” or“operation”.

FIG. 1 illustrates a block diagram depicting a system 11 for using aplurality of power levels in order to automatically and rapidly find thepower level, which allows a communication only with the closest mobiledevice 22 (willing to make a transaction), in accordance with an exampleembodiment. The system 11 shown in FIG. 1 includes a tag 10 that isassociated with and/or includes a power level adjustment module 8. Thetag 10 can adjust the power level (from a set of at least two differentpower levels) of the transceiver 16 and then send data (e.g.,advertisements, messages, etc.) and wait for a response from, forexample, the mobile device 22.

The tag 10 can be implemented in the context of a wireless system forenabling transactions on an associated network delivering services(e.g., advertisements, data, etc.) to end users in accordance with oneaspect of an exemplary embodiment. The tag 10 is a BLE enabled tag andthus can communicate via its transceiver 16 with BLE enabled devices,such as, for example, the mobile device 22. Note that the term “tag” asutilized herein can include any kind of device that is non-batteryoperated (e.g., a non-battery operated device connected to a powersupply). The term “tag” as utilized herein can also refer to any kind ofdevice that is battery operated.

The example embodiments shown in FIG. 1 allow for the emission of datafrom the tag 10 with different power levels in order to automaticallyand quickly determine a power level for receipt of data by mobile device22. This allows for a transaction with the closest mobile device (thedevice willing to make an official transaction), such as, for example,mobile device 22. In the example shown in FIG. 1, it can be assumed thatmobile device 22 is running an “official” application (which will bediscussed in more detail herein), and that this is the device thatactually should be receiving the data (e.g., advertisements, messages,etc.) emitted from the tag 10 via transceiver 16.

The tag 0 includes a power level adjustment module 8, which can beconfigured to detect “non-official” applications (which will bediscussed in more detail herein) that continuously answer and preventother applications to answer and/or change the emission power level byusing, for example, a DR (Decreasing Ramp) module 6 or a dichotomymodule 7 until the tag 10 receives an answer from another application.The DR module 6 can provide instructions for implementing a DRalgorithm, and the dichotomy module 7 can provide instructions forimplementing a dichotomy algorithm. The power level adjustment module 8may be implemented as a module that communicates with the memory 14 ofthe tag 10. As will be discussed shortly, the power level adjustmentmodule 8 can be implemented as a hardware module, a software module,and/or a combination of both hardware and software.

FIG. 2 illustrates a block diagram depicting a system 11 that utilizes aplurality of power levels to automatically and rapidly determine thepower level, which allows a communication only with the closest mobiledevice willing to make a transaction, in accordance with an alternativeexample embodiment. Note that in FIGS. 1-2, identical or similar partsare indicated by identical reference numerals. The example embodimentshown in FIG. 2 is an alternative version of the example embodimentdepicted in FIG. 1.

Although not shown in FIG. 2, the power level adjustment module 8depicted in FIG. 2 can include the DR module 6 and/or the dichotomymodule 7 shown in FIG. 1. The DR module 6 and the dichotomy module 7will be discussed in greater detail herein with respect to FIGS. 4-5.

Note that in most instances, a “module” can constitute a softwareapplication, but can also be implemented as both software and hardware(i.e., a combination of software and hardware). Generally, programmodules include, but are not limited to, routines, subroutines, softwareapplications, programs, objects, components, data structures, etc., thatperform particular tasks or implement particular data types andinstructions. Moreover, those skilled in the art will appreciate thatthe disclosed method and system may be practiced with other computersystem configurations, such as, for example, hand-held devices,multi-processor systems, data networks, microprocessor-based orprogrammable consumer electronics, networked PCs, minicomputers,mainframe computers, servers, and the like.

The term module as utilized herein may refer to a collection of routinesand data structures that perform a particular task or implements aparticular data type. Modules may be composed of two parts: aninterface, which lists the constants, data types, variable, and routinesthat can be accessed by other modules or routines; and animplementation, which is typically private (accessible only to thatmodule) and which includes source code that actually implements theroutines in the module. The term module may also simply refer to anapplication, such as a computer program designed to assist in theperformance of a specific task, such as word processing, accounting,inventory management, etc. A module may also refer to a hardwarecomponent that is equipped with software (e.g., software module ormodules). Thus, the power level adjustment module 8 depicted in FIGS.1-2 and FIGS. 4-5 herein can include modules (or sub-modules) such asthe DR module 6 and/or the dichotomy module 7.

One or more tags such as tag 10 can be implemented as a deployed serviceaccess point to the associated network, such as entrances, exits,vehicles, stops, barriers, parking lot gates, etc., each tag having aunique identifier, an irreversible counter, a master key, and a log ofprevious transactions. The tag need not be connected to any network,thus allowing the positioning of the tag on a variety of service accesspoints, e.g., on vehicles of a transportation system, on entrances tovenues, gates to parking lots, etc.

The tag 10 can be powered (e.g., self-contained power supply, notshown). The tag 10 includes a processor 12 in communication with memory14 and a transceiver 16. The processor 12 may include a random numbergenerator and other suitable components to facilitate the systems andmethods discussed hereinafter. The memory 14 may comprise non-volatileand/or volatile memory capable of storing various types of data. The tag10 may utilize symmetric cryptography (3DES, AES, etc.) or asymmetriccryptography (RSA, ECC, etc.). The memory 14 may include, for example,data 19 and a unique tag identifier (TagID) 18 associated with the tag10 and which can be supplied by a central system during deployment ofthe tag 10. The transceiver 16 of the tag 10 may correspond to anysuitable component capable of establishing bi-directional communicationbetween the tag 10 and user devices such as, for example, mobile device22 and/or other devices, such as a controller device (not shown).

In some example embodiments, the tag 10 may incorporate a low-cost NearField Communication (NFC) small component, which is powered orunpowered, which is also capable of communication with an NFC-enableduser device over a short distance (e.g., up to 10 cm), and which can beaffixed to a vehicle, station, turnstile, gate, barrier or otheraccoutrement associated with systems and networks delivering services,as illustrated and discussed in further detail herein. It should beappreciated, however, that the targeted usage of the disclosed powerlevel adjustment module 8 is primarily the case where BLE is usedinstead of NFC, because with NFC, the phone can only interrogate the tagat a very short distance and no collision is possible. With BLE, on theother hand, the phone will answer to an advertisement actively emittedby the tag. In addition, the phone should be close enough to guarantee aconscious act from its owner (this close distance may be verified by thetag using the RSSI (Received Signal Strength Indication)).

The terms “user device” or “mobile device” can be utilizedinterchangeably with one another and denotes a device owned by the userand able to contain and/or process an “application” for interacting withthe network delivering services to users. Examples of such a user deviceinclude, without limitation, mobile phones, personal data assistants,tablets, and other personal electronic devices. The user device ormobile device 22 may be NFC enabled and/or Bluetooth enabled (e.g., aBLE (Bluetooth Low Energy) enabled device) as well as capable of datacommunication with one or more wired or wireless networks, as discussedin greater detail herein. In some example embodiments, a user device ormobile device may be, for example, a computing device such as a wearablecomputing device (e.g., a smartwatch).

It can be appreciated that tags such as tag 10 may be located or placedin a variety of locations and on board vehicles such as, for example, apublic transportation vehicle (e.g., a sub, tramway, metro, train,taxis, etc.) or a private commercial transportation vehicle (e.g., anUber, Lyft, etc.).

FIG. 3 illustrates a schematic diagram depicting one example embodimentof the mobile device 22 (e.g., a client device) depicted in FIGS. 1-2and FIGS. 4-5, in accordance with an example embodiment. The mobiledevice 22 can function as a computing device capable of sending orreceiving signals through a wired or a wireless network such as, forexample, wireless network 110 depicted in FIG. 4.

The mobile device 22 may be implemented as, for example, a desktopcomputer or a portable device, such as a cellular telephone, aSmartphone, a display pager, a radio frequency (RF) device, an infrared(IR) device, a Personal Digital Assistant (PDA), a handheld computer, atablet computer, a laptop computer, a wearable computer, or anintegrated device combining various features, such as features of theforegoing devices, or the like. In a preferred example embodiment,however, it can be assumed that the mobile device 22 is a mobile devicesuch as, for example, a smartphone, tablet computing device, asmartwatch, or other wearable computing devices.

A client device such as mobile device 22 may vary in terms ofcapabilities or features. The claimed subject matter is intended tocover a wide range of potential variations. For example, a cell phonemay include a numeric keypad or a display of limited functionality, suchas a monochrome liquid crystal display (LCD) for rendering text andother media. In contrast, however, as another example, a web-enabledclient device may include one or more physical or virtual keyboards,mass storage, one or more accelerometers, one or more gyroscopes, globalpositioning system (GPS) or other location identifying type capability,or a display with a high degree of functionality, such as atouch-sensitive color 2D or 3D display, for example.

A client device such as mobile device 22 may include or may execute avariety of operating systems, such as operating system 241, including insome example embodiments, a personal computer operating system, such asa Windows®, iOS®, or Linux®, or a mobile operating system, such as iOS®,Android®, or Windows Mobile®, or the like. A client device such asmobile device 22 may include or may execute a variety of possibleapplications, such as a client software application enablingcommunication with other devices, such as communicating one or moremessages, such as via email, short message service (SMS), or multimediamessage service (MMS), including via a network, such as an online socialnetwork, including, for example, Facebook®, LinkedIn®, Twitter®,Flickr®, Google+®, to provide only a few possible examples.

A client device, such as mobile device 22, may also include or executean application to communicate content, such as, for example, textualcontent, multimedia content, or the like. A client device may alsoinclude or execute an application to perform a variety of possibletasks, such as browsing, searching, playing various forms of content,including locally stored or streamed video, or games (e.g., fantasysports leagues, etc.). The foregoing is provided to illustrate thatclaimed subject matter is intended to include a wide range of possiblefeatures or capabilities. Examples of such applications (or modules) caninclude a messenger 243, a browser 245, and other client application(s)or module(s) such as a tag module 247 that provides instructions forfacilitating interactivity and communications between the mobile device22 and the tag 10.

The example mobile device 22 shown in FIG. 3 generally includes a CPU(Central Processing Unit) 222 and/or other processors (not shown)coupled electronically via a system bus 224 to memory 230, power supply226, and a network interface 250. The memory 230 can be composed of RAM(Random Access Memory) 232 and ROM (Read Only Memory) 234. Other examplecomponents that may be included with mobile device 22 can include, forexample, an audio interface 252, a display 254, a keypad 256, anilluminator 258, and an input/output interface 260. In some exampleembodiments, a haptic interface 262 and a GPS (Global PositioningSystem) module or unit 264 along with a Bluetooth (BT) module 265 and anNFC (Near Field Communications) module 267 can also be electronicallycoupled via the system bus 224 to CPU 222, memory 230, power supply 226,and so on.

The BT (Bluetooth) module 265 can permit communication of mobile device22 with other devices, including Bluetooth and/or BLE beacons and/ortransponders as discussed herein. The near field communication (NEC)module 267 can facilitate NEC communication with other devicesincluding, e.g., an NEC beacon. With respect to the Bluetooth module265, it may be implemented as a Bluetooth Low Energy (BLE) module and/ora Bluetooth 4.0 module that implements communications using one or moreof BLE systems, standard Bluetooth systems, and/or iBeacon systemsspecifically. As understood herein, BLE may operate in the same spectrumrange (the 2.400 GHz-2.4835 GHz band) as classic Bluetooth technology,but may use a different set of channels. Instead of Bluetooth's seventynine 1-MHz channels, e.g., BLE employs forty 2-MHz channels. BLE maysend data within a channel using Gaussian frequency shift modulationwith a one megabyte per second data rate and a maximum transmissionpower of ten milliwatts (10 mW).

RAM 232 can store an operating system 241, provide for data storage 244,and the storage of applications 242 such as, for example, browser 245and messenger 243 applications. ROM 234 can include a BIOS (BasicInput/Output System) 240, which is a program that the CPU 222 utilizesto initiate the computing system associated with mobile device 22. BIOS240 can also manage data flow between operating system 241 andcomponents such as display 254, keypad 256, and so on.

Applications 242 can thus be stored in memory 230 and may be “loaded”(i.e., transferred from, for example, memory 230 or another memorylocation) for execution by the mobile device 22. Mobile device 22 canreceive user commands and data through, for example, the input/outputinterface 260. The mobile device 22 in accordance with instructions fromoperating system 241 and/or application(s) 242 may then act upon suchinputs. The interface 260, in some embodiments, can serve to displayresults, whereupon a user may supply additional inputs or terminate asession. The software application(s) 242 can include one or more modulessuch as modules 243, 245, 247, and so on, which can, for example,implement instructions or operations such as those described herein.

FIG. 4 illustrates a system 11 for improving BLE collision management,in accordance with an example embodiment. Note that in FIGS. 1-5 herein,similar or identical parts or elements are indicated by identicalreference numerals. System 11 shown in FIG. 4 is an alternative versionof the system 11 embodiments depicted in FIGS. 1-2. As shown in FIG. 4,the mobile device 22 can communicate with a wireless network 110 viapacket data communications. Another mobile device(s) 23 can alsocommunicate with the wireless network 110. Note that the mobiledevice(s) 23 may be a device that is similar to the mobile device 22shown in FIG. 3, but may vary in the type of device (e.g., a iPhoneversus an Android-based smartphone or a smartphone versus a tablecomputing device, etc.).

As indicated previously, the tag 10 may be located on or incorporatedinto a vehicle such as an automobile or public transportation vehicle(e.g., a city bus, a subway car, etc.) and can include the power leveladjustment module 8 as discussed previously. The tag 10 can beimplemented as a Bluetooth-enabled tag used in, for example, publictransport vehicles (e.g., buses, subways, trams, etc.) to enable travelvalidation with mobile phones such as the mobile device 22 depicted inthe various preferred and alternative embodiments shown in FIGS. 1-2 andFIGS. 4-5.

As indicated previously, the power level adjustment module 8 can includethe DR (Decreasing Ramp) module 6 and/or the dichotomy module 7. The DRmodule 6 maintains instructions for a decreasing ramp algorithm and thedichotomy module 7 maintains instructions for a dichotomy algorithm.

With the decreasing ramp algorithm employed by the DR module 6, thepower level can be decreased step-by-step from a maximum or “standard”level down to a level where, for example, the mobile device(s) 23 doesnot answer anymore. The step value may be constant (e.g., in milliwatts)giving an arithmetic progression of the power level, or in decibels, andin this case providing a geometric progression of the power level, ormay not be constant (e.g., based on previous experience) (e.g., usingprevious levels which succeeded in rejecting the mobile device(s) 23while still communicating with the mobile device 22).

With the dichotomy algorithm provided by the dichotomy module 7, at eachstep the power level can be set to a value between the last known levelwhere the mobile device(s) 23 still answers and the last known levelwhere no phone answers (starting from the minimum achievable powerlevel). The computation of the value may use arithmetic average,geometric average, harmonic average, or any other formula (e.g., basedon previous experience) (e.g., using previous levels which succeeded inrejecting the mobile device(s) 23 while still communicating with themobile device 22).

The wireless network 110 shown in FIG. 4 can be implemented as apacket-based wireless network that communicates via packet basedwireless data communications with the mobile device 22 and/or the mobiledevice(s) 23. The wireless network 110 may be, for example, a WAN (WideArea Network)/LAN (Local Area Network), a WiFi network, a cellularcommunications network, and so on. The wireless network 110 may furthercommunicate with a server 106, which can contain memory and processorcomponents, and which can store and process operations such as describedherein.

System 11 can thus manage the emission of data (e.g., advertisements,messages, etc.) from the BLE enabled tag 10. Data is emitted from thetag 10 via RF communications (e.g., such as BLE communications). Anoperation can be implemented to detect one or more non-officialapplications running on a mobile device (e.g., one or more nearby mobiledevices) such as, for example, mobile device(s) 23. In the scenarioshown in FIG. 4, it can be assumed that mobile device(s) 23 is running anon-official application and mobile device 22 is running the officialapplication. The emission power level for emitting data from tag 10 canbe automatically varied until an answer is received from an officialapplication running the mobile device 22 so as to prevent said mobiledevice(s) 23 running said non-official application from beginning orcompleting a transaction with respect to said data emitted from said tag10. The emission power level associated with the emission of data fromthe tag 10 can be varied utilizing, for example, the decreasing rampalgorithm employed by the decreasing ramp module 6 or the dichotomyalgorithm provided by the dichotomy module 7 shown, for example, in FIG.1.

Regarding non-official and official applications, there are two types ofnon-official applications. The first type (Type 1 Application) ofnon-official application involves an application that is configured ormade by modifying an official application to “look like” an officialapplication, and which may also be able to “complete a transaction”(depending on the expiry date of its keys or any other fraud detectionmechanism available in, for example, the tag 10). The second type (Type2 Application) of non-official application involves an application thatis “made from scratch” and which “only” (but always) answers the data(e.g., advertisements, messages, etc.) emitted from a tag such as tag10.

The tag has to reject both types of applications and can therefore(according to the disclosed embodiments) detect for Type 1 Applications,that a transaction has already completed and that the Type 1 Applicationshould not continuously answer to, for example, advertisement messagesand try to make a transaction; and for Type 2 Applications, that atransaction is not possible because the application does not continuewith an official sequence of messages after its answer to anadvertisement message. Therefore, the emission power level can beautomatically varied so as to prevent mobile device(s) 23 from“occupying the communication channel” (and not “completing atransaction”).

In some example embodiments, the server 106 may function as a contentserver that is configured to provide content via a network (e.g., aclient/server network) to other networks and devices. A content servermay, for example, host a site, such as a social networking site,examples of which may include, without limitation, Flickr®, Twitter®,Facebook®, LinkedIn®, or a personal user site (e.g., such as a bldg,vlog, online dating site, etc.). A content server may also host avariety of other sites, including but not limited to, business sites,educational sites, dictionary sites, encyclopedia sites, wikis,financial sites, government sites, etc.

A content server may further provide a variety of services that include,but are not limited to, web services, third-party services, audioservices, video services, email services, instant messaging (IM)services, SMS services, MMS services, FTP services, voice over IP (VOIP)services, calendaring services, photo services, or the like. Examples ofcontent may include text, images, audio, video, or the like, which maybe processed in the form of physical signals, such as electricalsignals, for example, or may be stored in memory, as physical states,for example. Examples of devices that may operate as a content serverinclude desktop computers, multiprocessor systems, microprocessor-type,or programmable consumer electronics, etc.

The wireless network 110 can couple devices so that communications maybe exchanged, such as between the server 106 and the mobile device 22 orother types of devices, including between wireless devices coupled via awireless network, for example. The wireless network 110 may also includemass storage, such as network-attached storage (NAS), a storage areanetwork (SAN), or other forms of computer or machine-readable media, forexample. A network may include the Internet, one or more Local AreaNetworks (LANs), one or more Wide Area Networks (WANs), wire-line typeconnections, wireless type connections, or any combination thereof.Likewise, sub-networks may employ differing architectures or may becompliant or compatible with differing protocols, may interoperatewithin a larger network. Various types of devices may, for example, bemade available to provide an interoperable capability for differingarchitectures or protocols. As one illustrative example, a router mayprovide a link between otherwise separate and independent LANs.

A communication link or channel may include, for example, analogtelephone lines, such as a twisted wire pair, a coaxial cable, full orfractional digital lines including T1, T2, T3, or T4 type lines,Integrated Services Digital Networks (ISDNs), Digital Subscriber Lines(DSLs), wireless links including satellite links, or other communicationlinks or channels, such as may be known to those skilled in the art.Furthermore, a computing device or other related electronic devices maybe remotely coupled to a network, such as via a telephone line or link,for example.

The wireless network 110 depicted in FIG. 4 may couple client deviceswith the network. That is, such a wireless network may employstand-alone ad-hoc networks, mesh networks, wireless LAN (WLAN)networks, cellular networks, or the like. A wireless network such aswireless network 110 can further include a system of terminals,gateways, routers, or the like coupled by wireless radio links, or thelike, which may move freely, randomly, or organize themselvesarbitrarily, such that network topology may change, at times evenrapidly. A wireless network may further employ a plurality of networkaccess technologies, including Long Term Evolution (LTE), WLAN, WirelessRouter (WR) mesh, or 2nd, 3rd, or 4th generation (2G, 3G, or 4G)cellular technology, or the like. Network access technologies may enablewide area coverage for devices, such as client devices with varyingdegrees of mobility, for example.

For example, a network may enable RF or wireless type communication viaone or more network access technologies, such as Global System forMobile communication (GSM), Universal Mobile Telecommunications System(UMTS), General Packet Radio Services (GPRS), Enhanced Data GSMEnvironment (EDGE), 3GPP Long Term Evolution (LTE), LTE Advanced,Wideband Code Division Multiple Access (WCDMA), Bluetooth, 802.11b/g/n,or the like. A wireless network may include virtually any type ofwireless communication mechanism by which signals may be communicatedbetween devices, such as a client device or a computing device, betweenor within a network, or the like.

Note that signal packets communicated via a network, such as a networkof participating digital communication networks (e.g., wireless network110) may be compatible with or compliant with one or more protocols.Signaling formats or protocols employed may include, for example,TCP/IP, UDP, DECnet, NetBEUI, IPX, AppleTalk, or the like. Versions ofthe Internet Protocol (IP) may include IPv4 or IPv6.

The Internet refers to a decentralized global network of networks. TheInternet includes Local Area Networks (LANs), Wide Area Networks (WANs),wireless networks, or long haul public networks that, for example, allowsignal packets to be communicated between LANs. Signal packets may becommunicated between nodes of a network, such as, for example, to one ormore sites employing a local network address. A signal packet may, forexample, be communicated over the Internet from a user site via anaccess node coupled to the Internet. Likewise, a signal packet may beforwarded via network nodes to a target site coupled to the network viaa network access node, for example. A signal packet communicated via theInternet may, for example, be routed via a path of gateways, servers,etc., that may route the signal packet in accordance with a targetaddress and availability of a network path to the target address.

FIG. 5 illustrates a system 11 for improving BLE collision management,in accordance with an alternative example embodiment. It can beappreciated that like the embodiment shown in FIG. 2, the system 11 canbe implemented with the power level adjustment module 8 and itssub-modules stored in memory 14 and then processed by the processor 12.Thus, in the example embodiment depicted in FIG. 5, the power leveladjustment module 8 is depicted as being maintained by the memory 14. Insuch a situation, it can be assumed that the power level adjustmentmodule 8 is a software module or primarily a software module, whereas inthe example embodiment depicted in FIG. 4, the module 8 may beimplemented as hardware, software, and/or a combination ofsoftware/hardware, depending on design considerations.

FIG. 6 illustrates a flow chart of operations depicting logicaloperational steps of a method 100 for BLE collision management, inaccordance with an example embodiment. The method 100 depicted in FIG. 6generally manages the emission (RF transmission) of data (e.g.,messages, advertisements, etc.) from a tag such as tag 10. As indicatedat block 102, a step or operation can be implemented for emitting datafrom a tag (e.g., tag 10) via RF communications (e.g., BLEcommunications) via the tag's transceiver (e.g., transceiver 16).Thereafter, as shown at block 104, a step or operation can beimplemented for detecting if a non-official application (“app”) isrunning on a first mobile device (e.g., such as the mobile device(s)23). If such a non-official app is detected as shown at decision block107, then as indicated thereafter at decision block 108, a step oroperation can be performed for varying the emission power level foremitting the data from the tag via the aforementioned RF communicationsuntil an answer is received from an official app running on anothermobile device so as to prevent the first mobile device running saidnon-official app from preventing said official application running onsaid another mobile device from initiating or completing a transactionwith respect to said data emitted from said tag via said REcommunications. Following processing of the operation depicted at block112, varying of the emission power level can then end. Thus, as shown inFIG. 6, the variation of the power level occurs until an official answeris received.

Note that the method 100 of reducing emission power level to avoiddetection by unwanted mobile devices in some instances lead to morecommunication errors such as the signal-to-noise ratio being reduced bythe power level reduction. Therefore, the method 100 and the variousother features discussed herein can be expanded and modified such thatas soon as another “app” is detected (e.g., in response to theadvertisement message), the tag power level may be increased whensending messages addressed to this particular application, in order tolimit the risk of communication errors (because the ambient noise is notconstant, because the user may slightly move its phone away from thetag, etc.). This increased power level may be the initial maximum or“standard” level or may be any level between the level at which the saidanother application answered and the initial maximum or “standard” levelused to continuously search for phones.

FIG. 7 illustrates a flow chart of operations depicting logicaloperational steps of a decreasing ramp algorithm 300, in accordance withan example embodiment. The algorithm (or method) 300 includes a numberof logical operational steps, examples of which are shown in FIG. 7. Asindicated at block 302 in FIG. 7, the process begins. Next, as shown atblock 304, a step or logical operation can be implemented in which theCurrent emission power level=maximum or “standard” emission power level.Then, as depicted at block 306, data can be emitted from, for example,tag 10 discussed previously.

Thereafter, as illustrated at decision block 308, a test is performed todetermine if an answer is received. If not, the process terminates asshown at block 318. If an answer is received (i.e., “Yes”), as shownnext at decision block 312, a test can be performed to determine if thereceived answer is associated with an official application. If not, thenthe emission power level is decreased, as shown at block 313 followed byprocessing of the operation shown at block 306 (“Emit data”) and so on.

Assuming that an official application is detected, as indicated atdecision block 312, an operation can be performed as shown at block 314to optionally set a higher emission power level. The transaction is thencompleted as shown at block 316 and the process then ends, as indicatedat block 318. The algorithm 300 shown in FIG. 7 thus provides for adecreasing ramp algorithm such as the previously discussed decreasingramp algorithm associated with the decreasing ramp module 6.

FIGS. 8A-8B illustrate a flow chart of operations depicting logicaloperational steps of a dichotomy algorithm 400, in accordance with anexample embodiment. As indicated at block 402, the process begins. Thealgorithm (or method) 400 includes a number of logical operationalsteps, examples of which are shown in FIGS. 8A-8B. Thereafter, asdepicted at block 404, a step or logical operation can be implemented inwhich the Current emission power level=maximum or “standard” emissionpower level. Next, as shown at block 406, a step or logical operationcan be implemented in which LKLWNPA (Last Known Level Where No PhoneAnswers)=0. Note that this feature is helpful in case the officialapplication can only be detected with the minimum possible emissionpower level. In this case, the algorithm will reduce several times theemission power level, down to this successful minimum where thenon-official application will not answer.

Then, as described at block 408, a step or operation can be implementedin which data is emitted from, for example, the tag 10 discussedpreviously. Next, as shown at decision block 410, a test is performed todetermine if an answer is received. If so, then as shown at block 412, atest is performed to determine if the received answer is associated withan official application. If the answer is “Yes,” then a step oroperation can be implemented as shown at block 414 to optionally set ahigher emission power level. The transaction is then completed, asindicated at block 416 and the process then terminates, as shown atblock 418.

Returning now to the decision block 410, assuming it is determined thatan answer was not received (i.e., “No” with respect to decision block410), then as shown at decision block 411, a test can be implemented todetermine if the Current emission power level=maximum or “standard”emission power level. If the answer is “Yes,” then the process thenterminates as shown at block 418. If the answer, however, is “No,” thenthe operation shown at block 413 is processed wherein LKLWNPA=currentemission power level, followed by the operation depicted at block 415 inwhich the emission power level is increased. Following completion of theoperation shown at block 415, the “Emit data” operation depicted atblock 408 is implemented and so on.

Returning now to the operation shown at decision block 412 (“Officialapplication?”), assuming the answer is “No,” then an operation can beprocessed as depicted at decision block 419 to determine if there is anAchievable lower emission power level>LKLWNPA (or, if there is a powerlevel both lower than the current emission power level and higher thanLKLWNPA). If not, then the process ends as shown at block 418.Otherwise, as indicated at block 421, the emission power level isdecreased, followed by the operation shown at block 408 (“Emit data”)and so on.

It will be appreciated that variations of the above-disclosed and otherfeatures and functions, or alternatives thereof, may be desirablycombined into many other different systems or applications. It will alsobe appreciated that various presently unforeseen or unanticipatedalternatives, modifications, variations or improvements therein may besubsequently made by those skilled in the art which are also intended tobe encompassed by the following claims.

What is claimed is:
 1. A method for managing emission of data from atag, said method comprising: emitting data from a tag via RFcommunications; detecting a non-official application running on a firstmobile device, wherein said non-official application comprises anunauthorized application and an official application comprises anauthorized application; and varying an emission power level for saidemitting of said data from said tag via said RF communications until ananswer is received from an official application running on anothermobile device so as to prevent said first mobile device running saidnon-official application from preventing said official applicationrunning on said another mobile device from initiating or completing atransaction with respect to said data emitted from said tag via said RFcommunications.
 2. The method of claim 1 wherein said RF communicationscomprises BLE (Bluetooth Low Energy) communications and wherein said tagcomprises a BLE enabled tag that includes a processor, a memory, and atransceiver, wherein said processor communicates with said memory andsaid transceiver and wherein said processor includes a random numbergenerator to facilitate secure communications and wherein said securecommunications further include symmetric cryptography or asymmetriccryptography.
 3. The method of claim 1 wherein varying said emissionpower level further comprises: varying said emission power level with adecreasing ramp algorithm.
 4. The method of claim 3 wherein saiddecreasing ramp, algorithm decreases said emission power level from amaximum level or a standard level to a level where said first mobiledevice does not answer anymore with respect to said data emitted by saidtag.
 5. The method of claim 1 wherein varying said emission power levelfurther comprises: varying said emission power level with a dichotomyalgorithm.
 6. The method of claim 5 wherein said dichotomy algorithmsets said emission power level to a value between a last known levelwhere said first mobile, device still answers with respect to said dataand a last known level where no mobile device answers.
 7. The method ofclaim 2 wherein said varying said emission power level further comprisesvarying said emission power level transmitted through said transceiverassociated with said tag.
 8. An apparatus for managing emission of datafrom a tag, said apparatus comprising: a tag that emits data from saidtag via RF communications, wherein if a non-official application isrunning on a first mobile device, wherein said non-official applicationcomprises an unauthorized application and an official applicationcomprises an authorized application, and wherein an emission power levelfor said emitting of said data from said tag via said RF communicationsis varied until an answer is received from an official applicationrunning on another mobile device so as to prevent said first mobiledevice running said non-official application from preventing saidofficial application running on said another mobile device frominitiating or completing a transaction with respect to said data emittedfrom said tag via said RF communications.
 9. The apparatus of claim 8wherein said RF communications comprises BLE (Bluetooth Low Energy)communications and wherein said tag comprises a BLE enabled tag thatincludes a processor, a memory, and a transceiver, wherein saidprocessor communicates with said memory and said transceiver and whereinsaid processor includes a random number generator to facilitate securecommunications.
 10. The apparatus of claim 8 wherein said emission powerlevel is varied with a decreasing ramp algorithm.
 11. The apparatus ofclaim 10 wherein said decreasing ramp algorithm decreases said emissionpower level from a maximum level or a standard level to a level wheresaid first mobile device does not answer anymore with respect to saiddata emitted by said tag.
 12. The apparatus of claim 8 wherein saidemission power level is varied with a dichotomy algorithm.
 13. Theapparatus of claim 12 wherein said dichotomy algorithm sets saidemission power level to a value between a last known level where saidfirst mobile device still answers with respect to said data and a lastknown level where no mobile device answers.
 14. The apparatus of claim 9wherein said varying said emission power level further comprises varyingsaid emission power level transmitted through said transceiverassociated with said tag.
 15. A system for managing emission of datafrom a tag, said system comprising: at least one processor; and anon-transitory computer-usable medium embodying computer program code,said computer-usable medium capable of communicating with said at leastone processor, said computer program code comprising instructionsexecutable by said at least one processor and configured for: emittingdata from a tag via RF communications; detecting a non-officialapplication running on a first mobile device, wherein said non-officialapplication comprises an unauthorized application and an officialapplication comprises an authorized application; and varying an emissionpower level for said emitting of said data from said tag via said RFcommunications until an answer is received from an official applicationrunning on another mobile device so as to prevent said first mobiledevice running said non-official application from preventing saidofficial application running on said another mobile device frominitiating or completing a transaction with respect to said data emittedfrom said tag via said RF communications.
 16. The system of claim 15wherein said RF communications comprises BLE (Bluetooth Low Energy)communications and wherein said tag comprises a BLE enabled tag thatincludes a processor, a memory, and a transceiver, wherein saidprocessor communicates with said memory and said transceiver and whereinsecure communications facilitated by said tag include symmetriccryptography and asymmetric cryptography.
 17. The system of claim 15wherein said instructions for varying said emission power level furthercomprise instructions for varying said emission power level with adecreasing ramp algorithm.
 18. The system of claim 17 wherein saiddecreasing ramp algorithm decreases said emission power level from amaximum level or a standard level to a level where said first mobiledevice does not answer anymore with respect to said data emitted by saidtag.
 19. The system of claim 15 wherein said instructions for varyingsaid emission power level further comprise instructions for varying saidemission power level with a dichotomy algorithm.
 20. The system of claim19 wherein said dichotomy algorithm sets said emission power level to avalue between a last known level where said first mobile device stillanswers with respect to said data and a last known level where no mobiledevice answers.